Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

F.9.1 StructureDefinition: QICore-DeviceUseRequest

This profile is marked as a draft.

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/qicore-deviceuserequest

Profile of DeviceUseRequest for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.

This profile was published on Fri, Feb 27, 2015 00:00+1100 as a draft by Health Level Seven International (Clinical Quality Information - QICore).

F.9.1.1 Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseRequest ∑0..*DeviceUseRequestA request for a patient to use or be given a medical device
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... deviceuserequest-reasonRejected 0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/deviceuserequest-reasonRejected
Binding: Reasons for rejecting device use request codes (example)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... bodySite[x] S ∑0..1CodeableConcept, Reference(QICore-BodySite)Target body site
Binding: SNOMED CT Body Structures (example)
... status ?! S∑0..1codeproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted
Binding: DeviceUseRequestStatus (required)
... device S ∑1..1Reference(QICore-Device)Device requested
... encounter S ∑0..1Reference(QICore-Encounter)Encounter motivating request
... identifier ∑0..*IdentifierRequest identifier
... indication ∑0..*CodeableConceptReason for request
Binding: Problem Value Set (preferred)
... notes ∑0..*stringNotes or comments
... prnReason ∑0..*CodeableConceptPRN
Binding: Problem Value Set (preferred)
... orderedOn S ∑0..1dateTimeWhen ordered
... recordedOn S ∑0..1dateTimeWhen recorded
... subject S ∑1..1Reference(QICore-Patient)Focus of request
... timing[x] ∑0..1Timing, Period, dateTimeSchedule for use
... priority ∑0..1coderoutine | urgent | stat | asap
Binding: DeviceUseRequestPriority (required)

doco Documentation for this format

todo

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseRequest ∑0..*DeviceUseRequestA request for a patient to use or be given a medical device
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... deviceuserequest-reasonRejected 0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/deviceuserequest-reasonRejected
Binding: Reasons for rejecting device use request codes (example)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... bodySite[x] S ∑0..1CodeableConcept, Reference(QICore-BodySite)Target body site
Binding: SNOMED CT Body Structures (example)
... status ?! S∑0..1codeproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted
Binding: DeviceUseRequestStatus (required)
... device S ∑1..1Reference(QICore-Device)Device requested
... encounter S ∑0..1Reference(QICore-Encounter)Encounter motivating request
... identifier ∑0..*IdentifierRequest identifier
... indication ∑0..*CodeableConceptReason for request
Binding: Problem Value Set (preferred)
... notes ∑0..*stringNotes or comments
... prnReason ∑0..*CodeableConceptPRN
Binding: Problem Value Set (preferred)
... orderedOn S ∑0..1dateTimeWhen ordered
... recordedOn S ∑0..1dateTimeWhen recorded
... subject S ∑1..1Reference(QICore-Patient)Focus of request
... timing[x] ∑0..1Timing, Period, dateTimeSchedule for use
... priority ∑0..1coderoutine | urgent | stat | asap
Binding: DeviceUseRequestPriority (required)

doco Documentation for this format

XML Template

JSON Template

todo

 

Other representations of profile: Schematron

F.9.1.2 Terminology Bindings

PathNameConformanceValueSet
DeviceUseRequest.language?extrequiredhttp://tools.ietf.org/html/bcp47
DeviceUseRequest.extension
[UriType[http://hl7.org/fhir/StructureDefinition/deviceuserequest-reasonRejected]]		Reasons for rejecting device use request codesexampleReasons for rejecting device use request codes
DeviceUseRequest.bodySite[x]SNOMED CT Body StructuresexampleSNOMED CT Body Structures
DeviceUseRequest.statusDeviceUseRequestStatusrequiredDeviceUseRequestStatus
DeviceUseRequest.indicationProblem Value SetpreferredProblem Value Set
DeviceUseRequest.prnReasonProblem Value SetpreferredProblem Value Set
DeviceUseRequest.priorityDeviceUseRequestPriorityrequiredDeviceUseRequestPriority

F.9.1.3 Constraints

IdPathDetailsRequirements
.